Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1638

reference
373-tree-1
name
1638
tree-preservation-order

undefined

373-tpo-1
uprn
address-text
point
POINT (-1.030371 50.884506)
geometry
MULTIPOLYGON (((-1.030329 50.884502,-1.030331 50.884510,-1.030336 50.884518,-1.030346 50.884524,-1.030358 50.884528,-1.030371 50.884529,-1.030384 50.884528,-1.030396 50.884524,-1.030405 50.884518,-1.030412 50.884511,-1.030414 50.884502,-1.030412 50.884494,-1.030406 50.884487,-1.030397 50.884480,-1.030372 50.884475,-1.030359 50.884476,-1.030347 50.884480,-1.030337 50.884486,-1.030331 50.884493,-1.030329 50.884502)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL